bitkeeper revision 1.1159.258.169 (42b35222QJFB1A-V4mSUnrUrLfA8xA)
authordsteklof@us.ibm.com[iap10] <dsteklof@us.ibm.com[iap10]>
Fri, 17 Jun 2005 22:43:46 +0000 (22:43 +0000)
committerdsteklof@us.ibm.com[iap10] <dsteklof@us.ibm.com[iap10]>
Fri, 17 Jun 2005 22:43:46 +0000 (22:43 +0000)
commit90865c024e1265787444ba83e98ed080a9150d18
tree550ddee78c0b17b76fb99885e86a3b88c17e7ec5
parent54a0093d8214fe2ec194e3f4332336daff7849c3
bitkeeper revision 1.1159.258.169 (42b35222QJFB1A-V4mSUnrUrLfA8xA)

[PATCH] RE: [Xen-devel] DOM0_GETDOMAININFO intended behavior

Ok... now that I (unintentionally) went overboard on this, why not just
document how it works and leave it as is?

signed-off-by: dsteklof@us.ibm.com
signed-off-by: ian@xensource.com
BitKeeper/etc/logging_ok
tools/libxc/xc.h